home *** CD-ROM | disk | FTP | other *** search
- Path: inforamp.net!ts44-07
- From: rmorin@inforamp.net (Randy Charles Morin)
- Newsgroups: comp.lang.c
- Subject: Re: finding a bug.. any suggestions ?
- Date: Fri, 02 Feb 96 18:05:47 GMT
- Organization: MiddleWorld SoftWare
- Message-ID: <4etjft$7s1@sam.inforamp.net>
- References: <823166642snz@willen.demon.co.uk>
- NNTP-Posting-Host: ts44-07.tor.inforamp.net
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <823166642snz@willen.demon.co.uk>,
- Adrian Parker <adrian@willen.demon.co.uk> wrote:
- >
- >Using Watcom 10.0a..
- >Creating a win3x DLL incorporating Watcom ODBC (wsql40 patch to level C)
- >Calling the DLL from PowerBuilder 4.0
- >
- >What happens is that in the first call to the DLL to perform an operation
- >the whole thing works fine. But the second time, doing exactly the same
- >operation it GPFs in an apparently innocuous place. Also, when I quit
- >windows after the GPF, it hangs. So I'm assuming some part of windows
- >is being corrupted too.
- >
- >I've checked everything I can think of..
- > all the malloc/free statements balance.
- > all the variables I assign data to with strcpy etc are large eough.
- > all the pointers I use are correctly set up.
- >
- >The only thing I can think of that might catch this bug is some kind of
- >memory leak detector.. anyone have any suggestions as to what I could use ?
- >
- >Hopefully,
- >Adrian
-
- I had the same problem.
- What I did was clean up my ODBC opens and closes and everything stabilized.
- By cleaning up, I mean I made certain that I responded to all ODBC errors and
- took the proper precautions when an error occured. I never used ODBC
- resources more than once. I would close every HSTMT after only one useage.
-
- Agrivar
-